<div id="update"></div>
<div class="header">
<p>
Previous: [[cvs: release--Indicate that a Module is no longer in use#release&mdash;Indicate that a Module is no longer in use|release]], Up: [[cvs: Guide to CVS commands#Guide to CVS commands|CVS commands]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>

----

<div id="update_002d_002d_002dBring-work-tree-in-sync-with-repository"></div>
=== update&mdash;Bring work tree in sync with repository ===
<div id="index-update-_0028subcommand_0029"></div>


* update <nowiki>[</nowiki>-ACdflPpR<nowiki>]</nowiki> <nowiki>[</nowiki>-I name<nowiki>]</nowiki> <nowiki>[</nowiki>-j rev <nowiki>[</nowiki>-j rev<nowiki>]]</nowiki> <nowiki>[</nowiki>-k kflag<nowiki>]</nowiki> <nowiki>[</nowiki>-r tag|-D date<nowiki>]</nowiki> <nowiki>[</nowiki>-W spec<nowiki>]</nowiki> files&hellip;

* Requires: repository, working directory.

* Changes: working directory.

After you&rsquo;ve run checkout to create your private copy
of source from the common repository, other developers
will continue changing the central source.  From time
to time, when it is convenient in your development
process, you can use the <code>update</code> command from
within your working directory to reconcile your work
with any revisions applied to the source repository
since your last checkout or update.  Without the <code>-C</code>
option, <code>update</code> will also merge any differences
between the local copy of files and their base revisions
into any destination revisions specified with <code>-r</code>,
<code>-D</code>, or <code>-A</code>.

 [[cvs: update options#update options|&bull; update options]]::              update options
 [[cvs: update output#update output|&bull; update output]]::               update output

This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>].
